Skip to content

[action] [PR:26245] [Nokia] Enable interrupts for all cores in BCM DNX devices#26369

Merged
mssonicbld merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/26245
Apr 1, 2026
Merged

[action] [PR:26245] [Nokia] Enable interrupts for all cores in BCM DNX devices#26369
mssonicbld merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/26245

Conversation

@mssonicbld
Copy link
Copy Markdown
Collaborator

Why I did it

BCM interrupts are not enabled for all the cores and it is enabled only for core=0

Work item tracking
  • Microsoft ADO (number only):

How I did it

Enabled the interrupt for every core in the device.

How to verify it

Verified in the DNX devices that the interrupts are enabled for all the devices.

Which release branch to backport (provide reason below if selected)

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • [x ] 202511

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

Signed-off-by: Sonic Build Admin [email protected]

A picture of a cute animal (not mandatory but encouraged)

<!--
     Please make sure you've read and understood our contributing guidelines:
     https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

     ** Make sure all your commits include a signature generated with `git commit -s` **

     If this is a bug fix, make sure your description includes "fixes #xxxx", or
     "closes #xxxx" or "resolves #xxxx"

     Please provide the following information:
-->

#### Why I did it
BCM interrupts are not enabled for all the cores and it is enabled only for core=0
##### Work item tracking
- Microsoft ADO **(number only)**:

#### How I did it
Enabled the interrupt for every core in the device.
#### How to verify it
Verified in the DNX devices that the interrupts are enabled for all the devices.
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->

#### Which release branch to backport (provide reason below if selected)

<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->

- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [x ] 202511

#### Tested branch (Please provide the tested image version)

<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->

- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->

#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->

<!--
 Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->

#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->

Signed-off-by: Sonic Build Admin <[email protected]>

#### A picture of a cute animal (not mandatory but encouraged)
@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Original PR: #26245

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@yxieca
Copy link
Copy Markdown
Contributor

yxieca commented Mar 24, 2026

/azpw ms_conflict

1 similar comment
@yxieca
Copy link
Copy Markdown
Contributor

yxieca commented Mar 25, 2026

/azpw ms_conflict

@yijingyan2
Copy link
Copy Markdown
Contributor

/azpw retry

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Retrying failed(or canceled) jobs...

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Retrying failed(or canceled) stages in build 1070399:

✅Stage Test:

  • Job impacted-area-kvmtest-t2 by Elastictest: retried.
  • Job impacted-area-kvmtest-t1-lag by Elastictest: retried.

@mssonicbld mssonicbld merged commit fcd4bcc into sonic-net:202511 Apr 1, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants